Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
499-tree-1
name
1600
tree-preservation-order

undefined

499-tpo-1
uprn
address-text
point
POINT (-1.036995 50.886592)
geometry
MULTIPOLYGON (((-1.036939 50.886586,-1.036941 50.886597,-1.036949 50.886607,-1.036962 50.886615,-1.036977 50.886621,-1.036995 50.886623,-1.037012 50.886621,-1.037028 50.886616,-1.037041 50.886608,-1.037049 50.886598,-1.037052 50.886587,-1.037050 50.886576,-1.037042 50.886566,-1.037030 50.886558,-1.037014 50.886552,-1.036996 50.886551,-1.036979 50.886552,-1.036963 50.886557,-1.036950 50.886565,-1.036942 50.886575,-1.036939 50.886586)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL